home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
bbsutil
/
jvas110.zip
/
JVARCSRV.DOC
< prev
next >
Wrap
Text File
|
1993-07-27
|
24KB
|
593 lines
JVArcServ V1.10
by John A. Vink
(c) 1992, 1993 Gidget Software Development.
July 22, 1993
Disclaimer
----------
Neither I, John A. Vink, nor Gidget Software Development, may be
held liable for any damage that running this software may cause
to your system.
Introduction
------------
JVArcServ is based on the InterNet utility Archie designed at
McGill University in Quebec, Canada. Archie allows users to
locate programs available via anonymous FTP from sites around the
world. Since there are thousands of anonymous FTP sites around
the world, each one holding several gigabytes of software, this
utility was a great sigh of relief. There are now eight Archie
servers in operation today.
JVArcServ does much the same thing for FidoNet as Archie does for
the InterNet. It will locate files that are available for file
request from other FidoNet or compatible network nodes.
Installation
------------
Installation is relatively simple. A directory has to be created
to hold all of the file lists from other systems and a
configuration file has to be set up.
Configuration
-------------
The default configuration file is named 'jvarcsrv.cfg' in the
current directory. You can change this with the '-c' command
line parameter. You can do something like:
JVARCSRV -ce:\files\jvas.cfg
This would use the file 'jvas.cfg' as the configuration file in
the directory 'e:\files'.
The following are the commands that you can use in the
configuration file. Do not include a '\' on the end of paths
unless you are referring to a root directory.
NODE <node>
This is where you put your network address. <node> must be
in the standard zzz:nnnn/dddd format where zzz represents a
zone number, nnnn represents a net number, and dddd
represents the node number. This line must appear once and
only once somewhere in the configuration file.
Example:
NODE 1:250/318
AKA <node>
This is where you place additional network addresses that
you may have. You must have a separate AKA statement for
each additional address you want to use. You can have as
many of these statements as you like.
Example:
AKA 89:480/124
ALIAS <alias>
By default, JVArcServ only recognizes messages addressed to
"JVArcServ". Using the ALIAS command, you can have
JVArcServ process messages addressed to other names. You
can have as many ALIAS statements as you like.
Example:
ALIAS ArcServ
ALIAS JVArc
NETFILES <path>
This is the path to your network file directory. JVArcServ
will look in this directory to find new file lists sent in
from other systems. This line must appear once and only
once somewhere in the configuration file.
Example:
NETFILES e:\quickbbs\netfiles
NETMAIL <path>
This is the path to your netmail directory. This line must
appear once and only once somewhere in the configuration
file.
Example:
NETMAIL e:\quickbbs\netmail
OUTPATH <path>
This is the path to your primary outbound area. Outbound
mail to zones other than your primary one will be placed in
the same path name with '.zzz' placed at the end where zzz
is the zone number. This line must appear once and only
once somewhere in the configuration file.
Example:
OUTPATH e:\quickbbs\outbound
In this case, mail sent to someone in zone 1 would be put
into the directory 'e:\quickbbs\outbound', while mail sent
to someone in zone 89 would be put into the directory
'e:\quickbbs\outbound.059'. (059 is hexadecimal for 89.)
LOG
This instructs JVArcServ to keep a log of all happenings.
The log will tell you who has made requests, what systems
have registered, and new file lists that have come in. By
default, the log is written to 'jvarcsrv.log' in the current
directory.
Example:
LOG
LOGFILENAME <filename>
This tells JVArcServ to use a different filename as the
logfile instead of the default value. This line has no
effect if LOG does not appear in the configuration file
somewhere as well.
Example:
LOGFILENAME e:\quickbbs\logfile.jas
MOTD <filename>
Message of the Day. This optional command will include the
textfile specified as <filename> at the top of every
response JVArcServ sends out. This only applies to
responses to inquiries and not to maintenance messages and
file request messages.
Example:
MOTD news.txt
FILELISTS <path>
This is the path to the directory which holds all of the
file lists from all the registered systems. This line must
appear once and only once somewhere in the configuration
file.
Example:
FILELISTS e:\jvasfile
ZONE <num> <desc>
This is where you tell JVArcServ which zones you support,
and what networks they are. While you should have at least
one of these statements, they are optional. JVArcServ uses
this information when a user selects the "LISTZONES"
command. You can have as many of these statements as you
wish.
Example:
ZONE 1 FidoNet
ZONE 89 IMEX
ORIGIN <string>
This is the line that is included on the end of return
messages to users, known as an origin line. You need not
include your address in <string> since it is tacked onto the
end of the origin line anyways.
Example:
ORIGIN Gidget Information Systems, Toronto
MAILER <mailer>
This is used to select the type of mailer that you have.
Valid <mailer> are Binkley and Frontdoor. This defines how
file requests are made. Using Binkley, the default, creates
a '.req' file and a '.flo' file. Using FrontDoor creates a
netmail message with the file request bit set.
Example:
MAILER BINKLEY
NOFORCEPHONE
This does not force the phone number in the incoming file
lists to conform to a predefined format. By default, the
phone number contained in new file lists are checked that